-
Notifications
You must be signed in to change notification settings - Fork 223
USHIFT-6427: Update script to wait for all containers to be ready in the pod #5979
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
/test e2e-aws-tests-bootc-release-arm |
|
@kasturinarra: This pull request references USHIFT-6427 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
f2670f2 to
0d7e6f8
Compare
|
/test e2e-aws-tests-bootc-release-arm |
0d7e6f8 to
2553b1e
Compare
|
/test e2e-aws-tests-bootc-release-arm |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: agullon, kasturinarra The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test e2e-aws-tests-bootc-release |
|
@kasturinarra: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
currently the code just waits for pod to be running but there may be a possibility that all containers in the pod might not go to ready state, so updating the code to make sure it waits until all the containers in the pod are ready.